home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20000114-20000217
/
000068_news@columbia.edu _Tue Jan 18 14:56:08 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2000-02-16
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id OAA20234
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 18 Jan 2000 14:56:07 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id OAA23212
for kermit.misc@watsun.cc.columbia.edu; Tue, 18 Jan 2000 14:40:50 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: jrd@cc.usu.edu (Joe Doupnik)
Subject: Re: MS-DOS Kermit, more capabalities
Message-ID: <8vfvgbrIQWo8@cc.usu.edu>
Date: 18 Jan 00 12:06:51 MDT
Organization: Utah State University
To: kermit.misc@columbia.edu
> Anyway, this has been a llllooonng reading for you all and this has been
> quite much longer for me to type it, i garantee that!... Time to go!...
>
> Salutations,
>
> Michel Samson
-------
<Snipping almost all 303 lines.>
SMTP (mail) is a full messy protocol and has no business being
conducted by a terminal emulator/Kermit file transfer program. The other
side needs a proper MX record and a receptive SMTP host, of which the latter
is not reasonable on desktop machines which are on and off a lot. This is
not the way to do email.
MSK can also mimic parts of being a web browser, as we do in class.
That's a technical curiosity and not a design decision. It's only that,
a curiosity and not a reason to make it a Lynx-II.
I have no plans of touching zmodem file transfer material. It is
a different universe to construct and that would both bloat MSK and make
life confusing to users because of the much different command sets. I need
not mention that it costs time to implement correctly, and perhaps licensing
fees to Omen Tech Inc to get the full specs (not just the quicky stuff).
Similarly, I have no plans on subverting MS-DOS Kermit to be yet
another transport layer blob. There are programs out there which can be used
and ought not be a speed limiting factor. And they are designed specifically
for this task. Again, user interfacing is another big problem, and that makes
life difficult for all but the very small number of prospective beneficiaries
of a transport blob approach. The internal technical details are more complex
that folks appreciate, even though "its only software." It could be I know
something about the matter.
I am open to discussions on providing an efficient transport layer
blob, as I crudely describe this approach, but only on a prepaid contract basis.
The same applies to existing BBS software: the Kermit protocol implementation
could be made better. If serious then please contact me directly with formal
specifics; it won't be cheap.
Lest folks misunderstand, I do listen and extract what I think
is being asked for (being polite here). From that I make a judgment about
what MSK can do to help. So far I think there is a pronounced mismatch and
that there are alternatives which do or can be made to work satisfactorily.
Further, there are alternatives of basic approach which obviate dealing with
BBS software and 8088 class machines; millions of people use them daily.
With that I think the matter has been explored here as far as it
needs to be.
Joe D.